Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix passing property and entity type names to ValueGenerated messages #29609

Merged
merged 1 commit into from
Nov 19, 2022

Conversation

ajcvickers
Copy link
Contributor

Fixes #29517

Parameter-reordering works for exception messages, but doesn't work for log messages. Also checked there are no other cases of this.

Fixes #29517

Parameter-reordering works for exception messages, but doesn't work for log messages.
Also checked there are no other cases of this.
@ajcvickers ajcvickers requested a review from a team November 18, 2022 14:14
Copy link

@tylerfelker tylerfelker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @ajcvickers! I slept on putting up a PR for this issue as my first contribution to efcore, but I did some digging already and want to share what I found with the testing for these logging methods. I think that the log message tests are sufficient, but the EventData message tests appear incomplete. One thing I found for the EventData messages is CoreEventIdTest.Every_eventId_has_a_logger_method_and_logs_when_level_enabled(). This tests that the EventData text matches the logged messages. However, after looking into it further, it only accounts for the CoreResources.LogValueGenerated log EventDefinition and does not account for LogValueGeneratedSensitive, LogTempValueGenerated, and LogTempValueGeneratedSensitive. I observed the gap in testing by leaving out the fixes on src/EFCore/Diagnostics/CoreLoggerExtensions.cs lines 2864-65 and running all tests with no failures. This can be seen with other "Sensitive" log events because they all share a CoreEventId with the non-sensitive variants.

I wanted to ask your opinion on whether the gap is acceptable before putting up a PR. You beat me to the punch here though! I'm curious about your thoughts but understand if the issue is too small to warrant the discussion.

I'll look for another issue to be my first 😄

@ajcvickers
Copy link
Contributor Author

@tylerfelker I had already done a fix (not pushed) for this yesterday before you commented--sorry for stepping on your toes.

Any improvements in the tests are always welcome.

@tylerfelker
Copy link

tylerfelker commented Nov 18, 2022

All good, @ajcvickers. There was no way to know without me commenting, so I'll be quicker next time.

As far as the test improvements go, I can make a PR for it.

I initially thought it would be nice if CoreEventIdTest were more exhaustive because it seems like we get the tests for free compared to the ones in ChangeTrackerTest. Still, I'm not sure about the complexity of doing that yet. I would imagine some changes to EventIdTestBase/TestEventLogging would be necessary, so the impact is likely broad since several other tests use them.

Expanding ChangeTrackerTest is more straightforward but would be on a case-by-case basis for each event being tested. I would see about adding a TestDiagnosticSource into the DI and doing additional asserts to check what's logged to it.

Any suggestions or preferences?

Edit: I didn't mean to hijack your PR. It's not clear to me yet if the test improvements should be part of this original issue or broken out into a separate one. I can create a new issue if appropriate?

@ajcvickers ajcvickers merged commit c771d25 into main Nov 19, 2022
@ajcvickers ajcvickers deleted the AsSmallAsAVerySmallThing1117 branch November 19, 2022 10:27
@ajcvickers
Copy link
Contributor Author

@tylerfelker I don't have any specific preferences here. Keep in mind that we try to keep the tests in a state where they would work with localized messages, so, make sure not to hardcode any logger messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ValueGenerated and ValueGeneratedSensitive have property/entity type swapped in message
3 participants